Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

Codecov Report

Patch coverage: 64.06% and project coverage change: -0.12% ⚠️

Comparison is base (99bc938) 95.09% compared to head (bed275c) 94.98%.

@@            Coverage Diff             @@
##           master    #2026      +/-   ##
==========================================
- Coverage   95.09%   94.98%   -0.12%     
==========================================
  Files         158      158              
  Lines       17420    17482      +62     
  Branches     1622     1630       +8     
==========================================
+ Hits        16566    16605      +39     
- Misses        641      662      +21     
- Partials      213      215       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This PR is our first proposal to add this functionality, but we have only an edge case in which we would like your opinion:

If the Subsection due date is configured to any date after the submission_due, the subsection due date is used instead. But we don't think this should be the case.

One solution we have in mind is to query for a UserDate (which stores individual date extensions) object related to the subsection and to the student.

What do you think? @Colin-Fredericks @Daniel-hershel

If the Subsection due date is configured to any date after the submission_due, the subsection due date is used instead. But we don't think this should be the case.

One solution we have in mind is to query for a UserDate (which stores individual date extensions) object related to the subsection and to the student.

@Ian2012 So we've got 5 dates at work here:

1. Subsection due date
2. ORA submission due date
3. ORA peer-grading due date
4. Learner extensions to the submission date
5. Learner extensions to the peer-grading date

My feeling is that learner extensions should override everything else, and the ORA dates should override the subsection due date. Does that make sense? Did I answer the wrong question?

@Ian2012 Thanks for these changes!

Hi @jmakowski1123, could you please create a feature ticket for this PR? Or will we not need one since there is an existing issue (#1959) that is being (partially) fixed here?

CC @e0d @mphilbrick211

@Ian2012 I just wanted to give you a heads up that we are planning to launch a very similar feature in the next week or so. I am going to meet with the lead engineer working on that project later today to review how this PR compares to the feature implementation we are planning to launch, and we will give an update after that meeting. Thank you for your contribution.

@Daniel-hershel thanks for the information

@Colin-Fredericks yes, that's the question. I will update the implementation to match this without tests, and wait for the result of your internal discussion

@Ian2012 Thanks for these changes!

Hi @jmakowski1123, could you please create a feature ticket for this PR? Or will we not need one since there is an existing issue (#1959) that is being (partially) fixed here?

CC @e0d @mphilbrick211

We shouldn't need one. If #1959 doesn't meet the full need, we should update it.

@Ian2012 I have met with our lead engineer on this project @jansenk , and my understanding is that the feature update we're about to launch will include the functionality included in this PR. The work we are finishing up will allow course authors to make a selection in studio that has 3 choices:

• align ORA due dates with subsection due date
• align ORA due dates with end of the course date
• leave ORA dates alone so they are only adjusted manually

My understanding is that this PR's functionality would essentially mirror the first option listed above. Please let me know if you think I'm missing something here and happy to keep talking it through.

@jansenk I know you were going to look into this a little more after our chat yesterday to so feel free to amend anything I'm saying here. thanks

CC: @e0d

Basically, it is. But also, allow instructors to extend a student's due date based on individual due date extensions.

As it aligns with your use case. Could you provide further instructions for this PR? @Daniel-hershel

@Ian2012 if you think there is still additional value in this PR that isn't represented in the work Jansen is doing, can you please help me understand what that additional value is?

The other question is whether anything in this PR will conflict with the release we are preparing to make. That is something that @jansenk would have to weigh in on.

Thanks

@Daniel-hershel: if the functionality you folks have been working on includes the use case of allow instructors to extend a student's due date based on individual due date extensions, then I think we're good to go since it's basically what we're attempting here. Should we close this PR then? Also, let us know when you release the new version so we can test it!

@jansenk can you please confirm the answer to the question @mariajgrimaldi is asking. Thanks!

@Ian2012 Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.

Based on this discussion #1959 (comment) this PR will be closed